Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

1. Plan process
   • Review specified requirements
   • Produce a plan to analyse the specified requirements
   • Plan the design and build of valid XML documentation allowing for iterative development
2. Analyse specified requirements
   • Determine and document the purpose, expectations and functionality of the XML document
   • Determine the hardware, software and tools needed to design the document
   • Determine the requirements for the document
   • Determine appropriate design methodologies, including using software engineering life cycle
3. Design and develop document
   • Decide on document type definition (DTD), if required
   • Define required entities, elements and their attributes
   • Produce the document following appropriate standards and declaring DTD, required entities, elements and their attributes, including associated graphics or sounds
4. Test document
   • 4.1 Test document off-line against specifications and confirm document's validity
   • Test, where appropriate, the document online against specifications and with a representative audience
   • Analyse test results and confirm document’s validity

Required Skills

Required skills

analytical skills to analyse document requirements and data environment

communication skills to liaise with clients

literacy skills to read required documents

problemsolving skills to address issues in design

technical skills to

collect and disseminate data

use XML during development

Required knowledge

Copyleft and Free Software Foundation

copyright and intellectual property

document object model

introductory knowledge of business process and information modelling

metamodelling

standard generalised markup language SGML

United Nations Centre for Trade Facilitation and Electronic Business UNCEFACT modelling methodology

unifiedmodelling language

web technologies

XLT and XSLT

Evidence Required

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria required skills and knowledge range statement and the Assessment Guidelines for the Training Package

Overview of assessment
Critical aspects for assessment and evidence required to demonstrate competency in this unit	Evidence of the ability to respond to requirements produce a valid XML document test the XML document evaluate the test results
Context of and specific resources for assessment	Assessment must ensure access to appropriate learning and assessment support when required modified equipment for people with special needs client or business requirements XML parser or IE XML authoring tool
Method of assessment	A range of assessment methods should be used to assess practical skills and knowledge The following examples are appropriate for this unit evaluation of candidates XML document review of candidates test results and test analysis verbal or written questioning to determine candidates knowledge of requirements XML and testing
Guidance information for assessment	Holistic assessment with other units relevant to the industry sector workplace and job role is recommended where appropriate Assessment processes and techniques must be culturally appropriate and suitable to the communication skill level language literacy and numeracy capacity of the candidate and the work being performed Indigenous people and other people from a nonEnglish speaking background may need additional support In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge

---

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

XML may include:	electronic business using eXtensible markup language (ebXML).
Hardware may include:	modems and other connectivity devices, such as asymmetric digital subscriber line (ADSL) modems networks personal computers remote sites servers workstations.
Software may include:	commercial software applications in-house or customised software organisation-specific software packaged software.
Tools may include:	Easy XML 1.0 eXml Editor QuickSilver 1.0 XML Suite XML Bean Suite XML Pro 2.0.
Standards may include:	W3C DOM specification, XML 1.0 (current edition), W3C XML instances, W3C XML DTDs, W3C XML DTDs, and ISO SGML meta-DTDs ebXML repository and registry specification ebXML requirements specification version 1.0 ebXML technical architecture specification ebXML transport, routing and packaging specification ISO 10646 Character encoding ISO 11179/3 Metadata repository ISO 8601:2000 Date/time/number data typing ISO/IEC 14662 Open-Edi Reference Model OASIS registry/repository technical specification RFC 2119 Keywords for use in RFCs to indicate requirement levels UN/CEFACT modelling methodology (UMM) W3C XML v1.0 second edition specification.

---